Skip to content

ci: skip dev/latest release on workflow-only changes#6083

Open
ale7714 wants to merge 1 commit into
mainfrom
ci/skip-dev-release-on-workflow-only-changes
Open

ci: skip dev/latest release on workflow-only changes#6083
ale7714 wants to merge 1 commit into
mainfrom
ci/skip-dev-release-on-workflow-only-changes

Conversation

@ale7714

@ale7714 ale7714 commented Jun 4, 2026

Copy link
Copy Markdown
Member

A push to main runs main.yml, which both tests and publishes a dev/latest release. We don't want to cut a dev release when a merge only touches workflow YAML, but we DO still want tests/lint and the license check to run.

Add a changes job (dorny/paths-filter) that flags whether the push touched anything outside .github/workflows/**, and gate only the build/deploy/droid/cli jobs on it. The deploy jobs cascade-skip via their build needs. The test and license_finder jobs are left ungated so they always run. workflow_dispatch is unaffected (the gate short-circuits when event_name != 'push').

@ale7714 ale7714 requested a review from abe-winter June 4, 2026 22:42
@viambot viambot added the safe to test This pull request is marked safe to test from a trusted zone label Jun 4, 2026
@ale7714

ale7714 commented Jun 4, 2026

Copy link
Copy Markdown
Member Author

i was aggressive in my other pr

@abe-winter abe-winter left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

what if my workflow change is a change to how the deployment logic works? in that case, do I want the deploy to run?

(but this PR is fine to merge if needed)

@viamrobotics-overwatch

Copy link
Copy Markdown

Hey @ale7714 — this PR has been approved and CI has been green for 5+ business days. Ready to merge?

Auto-comment from overwatch. Will not re-nudge for 7 days.

@ale7714 ale7714 force-pushed the ci/skip-dev-release-on-workflow-only-changes branch from 3c7329a to fc41295 Compare June 11, 2026 19:56
@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Jun 11, 2026
A push to main runs main.yml, which both tests and publishes a dev/latest
release. We don't want to cut a dev release when a merge only touches CI
workflow YAML, but we DO still want tests/lint and the license check to run.

Add a `changes` job (dorny/paths-filter) and gate the build/deploy/droid/cli
jobs on it. The release still runs for any non-workflow change OR for edits to
the build/deploy workflows themselves, so deploy-logic changes get validated
(per review feedback). It is skipped only when a push touches solely
non-release workflow YAML (e.g. test, claude, labeler). The deploy jobs
cascade-skip via their build `needs`; test and license_finder are left ungated.
workflow_dispatch is unaffected (the gate short-circuits when event != 'push').

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ale7714 ale7714 force-pushed the ci/skip-dev-release-on-workflow-only-changes branch from fc41295 to 8effcec Compare June 11, 2026 20:35
@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test This pull request is marked safe to test from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants